Capability Pattern: 8.11 Confidence in the use of software tools
This practice details the tasks required to be carried out to qualify software tools. Even if the tool has been prequalified by a tool vendor the organization must confirm the validity of the tool confidence level or qualification, prior to the software tool being used for the development of safety related item or element.
Extends: 8.11 Confidence in the use of software tools
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Purpose
To ensure that the software tools employed on a safety related project are suitable to be used to tailor the activities or tasks required by ISO 26262. This task provides the criteria to evaluate the required level of confidence in a tool and means for the qualification of the software tool.
Relationships
Description

A software tool used in the development of a system, its software or hardware elements, can support or enable a tailoring of the safety-lifecycle, by the tailoring of the activities and tasks required by ISO 26262. In such cases confidence is needed that the software tool effectively achieves the following goals:

a) the risk of systematic faults in the developed product due to malfunctions of the software tool leading to erroneous outputs is minimized, and

b) the development process is adequate with respect to compliance with ISO 26262, if activities or tasks required by ISO 26262 rely on the correct functioning of the software tool used.

Software tools  this instance are not limited to tools for creating the underlying SW used in the item or element but any SW tool that is employed as part of the development process for a safety related item or element. Typical examples are compilers, requirements management tools (Rational DOORS has been qualified by the tUV) and test generation tools. Code generation tools do not need to be qualified when used in conjunction with a qualified test tools as the test tool should find any errors that have been introduced by the code generation tool. A good example of this is using Rational Rhapsody for code generation in combination with the Rational Rhapsody Test Conductor (which is qualified by TUV).

To determine the required level of confidence in a software tool used within development the following criteria are evaluated:

The possibility that the malfunctioning software tool and its corresponding erroneous output can introduce or fail to detect errors in a safety-related item or element being developed, and

The confidence in preventing or detecting such errors in its corresponding output.

To evaluate the confidence in prevention or detection measures, measures internal to the software tool (e.g. monitoring) as well as measures external to the software tool (e.g. guidelines, tests, reviews) implemented in the development process of the safety-related item or element are considered and can be assessed.

If indicated by the determined tool confidence level, then appropriate qualification methods are applied to comply with both this tool confidence level and the maximum ASIL of all the safety requirements allocated to the item or element that is to be developed using the software tool. Otherwise there is no need to apply such qualification methods.

Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
Planned
Repeatable